SherbyNet - /page/wikibook/entry.mu

Micron Document

<!DOCTYPE html>

<title>Router (computing)</title>

</head>

Router (computing)

</h1>

</header>

/* start https://en.wikipedia.org/ */

.mw-parser-output .hatnote{font-style:italic}.mw-parser-output div.hatnote{padding-left:1.6em;margin-bottom:0.5em}.mw-parser-output .hatnote i{font-style:normal}.mw-parser-output .hatnote+link+.hatnote{margin-top:-0.5em}@media print{body.ns-0 .mw-parser-output .hatnote{display:none!important}}

/* end https://en.wikipedia.org/ */

</style><div role="note" class="hatnote navigation-not-searchable">This article is about the network device. For other uses, see <a href="Router_(disambiguation)" class="mw-redirect mw-disambig" title="Router (disambiguation)">Router (disambiguation)</a>.</div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .tmulti .multiimageinner{display:flex;flex-direction:column}.mw-parser-output .tmulti .trow{display:flex;flex-direction:row;clear:left;flex-wrap:wrap;width:100%;box-sizing:border-box}.mw-parser-output .tmulti .tsingle{margin:1px;float:left}.mw-parser-output .tmulti .theader{clear:both;font-weight:bold;text-align:center;align-self:center;background-color:transparent;width:100%}.mw-parser-output .tmulti .thumbcaption{background-color:transparent}.mw-parser-output .tmulti .text-align-left{text-align:left}.mw-parser-output .tmulti .text-align-right{text-align:right}.mw-parser-output .tmulti .text-align-center{text-align:center}@media all and (max-width:720px){.mw-parser-output .tmulti .thumbinner{width:100%!important;box-sizing:border-box;max-width:none!important;align-items:center}.mw-parser-output .tmulti .trow{justify-content:center}.mw-parser-output .tmulti .tsingle{float:none!important;max-width:100%!important;box-sizing:border-box;text-align:center}.mw-parser-output .tmulti .tsingle .thumbcaption{text-align:left}.mw-parser-output .tmulti .trow>.thumbcaption{text-align:center}}@media screen{html.skin-theme-clientpref-night .mw-parser-output .tmulti .multiimageinner span:not(.skin-invert-image):not(.skin-invert):not(.bg-transparent) img{background-color:white}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .tmulti .multiimageinner span:not(.skin-invert-image):not(.skin-invert):not(.bg-transparent) img{background-color:white}}

/* end https://en.wikipedia.org/ */

</style><div class="thumb tmulti tright"><div class="thumbinner multiimageinner" style="width:408px;max-width:408px"><div class="trow"><div class="tsingle" style="width:202px;max-width:202px"><div class="thumbimage"></div><div class="thumbcaption">Rack containing a service-provider–class router connected to multiple networks</div></div><div class="tsingle" style="width:202px;max-width:202px"><div class="thumbimage"></div><div class="thumbcaption">A home–class router with wireless capabilities; many home routers like this example combine router, <a href="Wireless_access_point" title="Wireless access point">wireless access point</a>, <a href="Network_switch" title="Network switch">switch</a> and <a href="Modem" title="Modem">modem</a> into one single unit (see also <a href="Residential_gateway" title="Residential gateway">residential gateway</a>)</div></div></div></div></div>

A router<a href="#cite_note-2">[a]</a> is a <a href="Computer" title="Computer">computer</a> and <a href="Networking_device" class="mw-redirect" title="Networking device">networking device</a> that <a href="Packet_forwarding" title="Packet forwarding">forwards</a> <a href="Data_packet" class="mw-redirect" title="Data packet">data packets</a> between <a href="Computer_network" title="Computer network">computer networks</a>, including <a href="Internetworks" class="mw-redirect" title="Internetworks">internetworks</a> such as the global <a href="Internet" title="Internet">Internet</a>.<a href="#cite_note-3">[2]</a><a href="#cite_note-Medhi-4">[3]</a><a href="#cite_note-Kundu-5">[4]</a>

Routers perform the "traffic directing" functions on the Internet. A router is connected to two or more data lines from different <a href="IP_network" class="mw-redirect" title="IP network">IP networks</a>. When a data packet comes in on a line, the router reads the <a href="Network_address" title="Network address">network address</a> information in the packet header to determine the ultimate destination. Then, using information in its <a href="Routing_table" title="Routing table">routing table</a> or <a href="Routing_policy" class="mw-redirect" title="Routing policy">routing policy</a>, it directs the packet to the next network on its journey. Data packets are forwarded from one router to another through an <a href="Internetwork" class="mw-redirect" title="Internetwork">internetwork</a> until it reaches its destination <a href="Node_(networking)" title="Node (networking)">node</a>.<a href="#cite_note-6">[5]</a>

The most familiar type of <a href="Internet_Protocol" title="Internet Protocol">IP</a> routers are <a href="Residential_gateway" title="Residential gateway">home and small office routers</a> that forward <a href="IP_packet_(disambiguation)" class="mw-redirect mw-disambig" title="IP packet (disambiguation)">IP packets</a> between the home computers and the Internet. More sophisticated routers, such as enterprise routers, connect large business or ISP networks to powerful <a href="Core_router" title="Core router">core routers</a> that forward data at high speed along the <a href="Optical_fiber" title="Optical fiber">optical fiber</a> lines of the <a href="Internet_backbone" title="Internet backbone">Internet backbone</a>.

Routers can be built from standard computer parts but are mostly <a href="Embedded_system" title="Embedded system">specialized purpose-built computers</a>. Early routers used <a href="Software" title="Software">software</a>-based forwarding, running on a <a href="CPU" class="mw-redirect" title="CPU">CPU</a>. More sophisticated devices use <a href="Application-specific_integrated_circuit" title="Application-specific integrated circuit">application-specific integrated circuits</a> (ASICs) to increase performance or add advanced filtering and <a href="Firewall_(computing)" title="Firewall (computing)">firewall</a> functionality.

<div class="mw-heading mw-heading2"><h2 id="History">History</h2></div>

The concepts of a switching node using software and an interface computer were first proposed by <a href="Donald_Davies" title="Donald Davies">Donald Davies</a> in 1966 for the <a href="NPL_network" title="NPL network">NPL network</a>.<a href="#cite_note-7">[6]</a><a href="#cite_note-8">[7]</a><a href="#cite_note-9">[8]</a> The same idea was conceived by <a href="Wesley_A._Clark" title="Wesley A. Clark">Wesley Clark</a> the following year for use in the <a href="ARPANET" title="ARPANET">ARPANET</a>, which were named <a href="Interface_Message_Processor" title="Interface Message Processor">Interface Message Processors</a> (IMPs).<a href="#cite_note-:2-10">[9]</a> The first interface computer was implemented at the <a href="National_Physical_Laboratory_(United_Kingdom)" title="National Physical Laboratory (United Kingdom)">National Physical Laboratory</a> in the United Kingdom in early 1969, followed later that year by the IMPs at the <a href="University_of_California%2C_Los_Angeles" title="University of California, Los Angeles">University of California, Los Angeles</a>, the <a href="Stanford_Research_Institute" class="mw-redirect" title="Stanford Research Institute">Stanford Research Institute</a>, the <a href="University_of_California%2C_Santa_Barbara" title="University of California, Santa Barbara">University of California, Santa Barbara</a>, and the <a href="University_of_Utah_School_of_Computing" title="University of Utah School of Computing">University of Utah School of Computing</a> in the United States.<a href="#cite_note-:22-11">[10]</a><a href="#cite_note-12">[11]</a><a href="#cite_note-13">[12]</a><a href="#cite_note-C._Hempstead,_W._Worthington-14">[13]</a> All were built with the <a href="Honeywell_316" title="Honeywell 316">Honeywell 516</a>. These computers had fundamentally the same functionality as a router does today.

The idea for a router (called a <a href="Gateway_(telecommunications)" title="Gateway (telecommunications)">gateway</a> at the time) initially came about through an international group of computer networking researchers called the <a href="International_Network_Working_Group" title="International Network Working Group">International Network Working Group</a> (INWG).<a href="#cite_note-15">[14]</a> These gateway devices were different from most previous <a href="Packet_switching" title="Packet switching">packet switching</a> schemes in two ways. First, they connected dissimilar kinds of networks, such as <a href="Serial_line" class="mw-redirect" title="Serial line">serial lines</a> and <a href="Local_area_network" title="Local area network">local area networks</a>. Second, they were <a href="Connectionless" class="mw-redirect" title="Connectionless">connectionless</a> devices, which had no role in assuring that traffic was delivered reliably, leaving that function entirely to the <a href="Host_(network)" title="Host (network)">hosts</a>.<a href="#cite_note-16">[15]</a> This particular idea, the <a href="End-to-end_principle" title="End-to-end principle">end-to-end principle</a>, was contained in the work of Donald Davies.<a href="#cite_note-:5-17">[16]</a><a href="#cite_note-Pelkey8.3-18">[17]</a>

The concept was explored in practice by various groups, with the intention to produce a working system for <a href="Internetworking" title="Internetworking">internetworking</a>. There were three notable contemporaneous programs. The first was an implementation directed by <a href="Louis_Pouzin" title="Louis Pouzin">Louis Pouzin</a> of the <a href="CYCLADES" title="CYCLADES">CYCLADES</a> network, which was designed and developed during 1972-3.<a href="#cite_note-:3-19">[18]</a><a href="#cite_note-20">[19]</a><a href="#cite_note-Bennett2009-21">[20]</a> The second was program at <a href="Xerox_PARC" class="mw-redirect" title="Xerox PARC">Xerox PARC</a> to explore new networking technologies, which produced the <a href="PARC_Universal_Packet" title="PARC Universal Packet">PARC Universal Packet</a> system. Some time after early 1974, the first Xerox routers became operational. Due to corporate intellectual property concerns, it received little attention outside Xerox for years.<a href="#cite_note-22">[21]</a><a href="#cite_note-23">[22]</a> The third was a <a href="DARPA" title="DARPA">DARPA</a>-initiated program, which began during 1973-4. This drew on the work of the other two programs,<a href="#cite_note-Cerf-1974-24">[23]</a> expanded significantly, and went on to create the <a href="TCP/IP" class="mw-redirect" title="TCP/IP">TCP/IP</a> architecture in use today.<a href="#cite_note-25">[24]</a><a href="#cite_note-26">[25]</a> <a href="University_College_London" title="University College London">University College London</a> (UCL) provided a gateway between <a href="Internet_in_the_United_Kingdom#Early_years" title="Internet in the United Kingdom">British research groups</a> and the ARPANET from 1973 until the late 1980s, latterly using <a href="SATNET" title="SATNET">SATNET</a>.<a href="#cite_note-:9-27">[26]</a><a href="#cite_note-28">[27]</a><a href="#cite_note-29">[28]</a>

The first true IP router was developed by Ginny Travers at <a href="BBN_Technologies" class="mw-redirect" title="BBN Technologies">BBN</a>, as part of that DARPA-initiated effort, during 1975–1976.<a href="#cite_note-30">[29]</a><a href="#cite_note-31">[30]</a> By the end of 1976, three <a href="PDP-11" title="PDP-11">PDP-11</a>-based routers were in service in the experimental prototype Internet.<a href="#cite_note-32">[31]</a> Mike Brecia, Ginny Travers, and Bob Hinden received the <a href="IEEE_Internet_Award" title="IEEE Internet Award">IEEE Internet Award</a> for early IP routers in 2008.<a href="#cite_note-33">[32]</a>

The first multiprotocol routers were independently created by staff researchers at <a href="MIT" class="mw-redirect" title="MIT">MIT</a> and <a href="Stanford" class="mw-redirect" title="Stanford">Stanford</a> in 1981 and both were also based on PDP-11s. Stanford's router program was led by <a href="William_Yeager" title="William Yeager">William Yeager</a> and MIT's by <a href="Noel_Chiappa" title="Noel Chiappa">Noel Chiappa</a>.<a href="#cite_note-34">[33]</a><a href="#cite_note-35">[34]</a><a href="#cite_note-36">[35]</a><a href="#cite_note-37">[36]</a> Virtually all networking now uses TCP/IP, but multiprotocol routers are still manufactured. They were important in the early stages of the growth of computer networking when protocols other than TCP/IP were in use. Modern routers that handle both IPv4 and IPv6 are multiprotocol but are simpler devices than ones processing AppleTalk, DECnet, IPX, and Xerox protocols.

From the mid-1970s and in the 1980s, general-purpose <a href="Minicomputer" title="Minicomputer">minicomputers</a> served as routers. Modern high-speed routers are <a href="Network_processor" title="Network processor">network processors</a> or highly specialized computers with extra <a href="Hardware_acceleration" title="Hardware acceleration">hardware acceleration</a> added to speed both common routing functions, such as packet forwarding, and specialized functions such as <a href="IPsec" title="IPsec">IPsec</a> encryption. There is substantial use of <a href="Linux" title="Linux">Linux</a> and <a href="Unix" title="Unix">Unix</a> software-based machines, running <a href="Open-source_software" title="Open-source software">open source</a> routing code, for research and other applications. The <a href="Cisco_IOS" title="Cisco IOS">Cisco IOS</a> operating system was independently designed. Major router operating systems, such as <a href="Junos" class="mw-redirect" title="Junos">Junos</a> and <a href="NX-OS" class="mw-redirect" title="NX-OS">NX-OS</a>, are extensively modified versions of Unix software.

<div class="mw-heading mw-heading2"><h2 id="Operation">Operation</h2></div>

When multiple routers are used in interconnected networks, the routers can exchange information about destination addresses using a <a href="Routing_protocol" title="Routing protocol">routing protocol</a>. Each router builds up a <a href="Routing_table" title="Routing table">routing table</a>, a list of routes, between two computer systems on the interconnected networks.<a href="#cite_note-38">[37]</a><a href="#cite_note-Cisco_2022_u602-39">[38]</a>

The software that runs the router is composed of two functional processing units that operate simultaneously, called planes:<a href="#cite_note-40">[39]</a>

<ul><li><a href="Control_plane" title="Control plane">Control plane</a>: A router maintains a routing table that lists which route should be used to forward a data packet, and through which physical interface connection. It does this using internal pre-configured directives, called <a href="Static_route" class="mw-redirect" title="Static route">static routes</a>, or by learning routes <a href="Dynamic_routing" title="Dynamic routing">dynamically</a> using a routing protocol. Static and dynamic routes are stored in the routing table. The control-plane logic then strips non-essential directives from the table and builds a <a href="Forwarding_information_base" title="Forwarding information base">forwarding information base</a> (FIB) to be used by the forwarding plane.</li>

<li><a href="Forwarding_plane" class="mw-redirect" title="Forwarding plane">Forwarding plane</a>: This unit forwards the data packets between incoming and outgoing interface connections. It reads the <a href="Header_(computing)" title="Header (computing)">header</a> of each packet as it comes in, matches the destination to entries in the FIB supplied by the control plane, and directs the packet to the outgoing network specified in the FIB.</li></ul>

<div class="mw-heading mw-heading2"><h2 id="Applications">Applications</h2></div>

A router may have interfaces for multiple types of <a href="Physical_layer" title="Physical layer">physical layer</a> connections, such as copper cables, <a href="Fiber_optic" class="mw-redirect" title="Fiber optic">fiber optic</a>, or <a href="Wireless" title="Wireless">wireless</a> transmission. It can also support multiple <a href="Network_layer" title="Network layer">network layer</a> transmission standards. Each network interface is used to enable data packets to be forwarded from one transmission system to another. Routers may also be used to connect two or more logical groups of computer devices known as <a href="Subnets" class="mw-redirect" title="Subnets">subnets</a>, each with a unique <a href="Network_prefix" class="mw-redirect" title="Network prefix">network prefix</a>.

Routers may provide connectivity within enterprises, between enterprises and the Internet, or between <a href="Internet_service_provider" title="Internet service provider">internet service providers</a>' (ISPs') networks, they are also responsible for directing data between different networks.<a href="#cite_note-41">[40]</a> The largest routers (such as the <a href="Cisco_CRS-1" class="mw-redirect" title="Cisco CRS-1">Cisco CRS-1</a> or <a href="Juniper_Networks" title="Juniper Networks">Juniper</a> PTX) interconnect the various ISPs, or may be used in large enterprise networks.<a href="#cite_note-42">[41]</a> Smaller routers usually provide connectivity for typical home and office networks.

All sizes of routers may be found inside enterprises.<a href="#cite_note-port-43">[42]</a> The most powerful routers are usually found in ISPs, academic and research facilities. Large businesses may also need more powerful routers to cope with ever-increasing demands of <a href="Intranet" title="Intranet">intranet</a> data traffic. A <a href="Hierarchical_internetworking_model" title="Hierarchical internetworking model">hierarchical internetworking model</a> for interconnecting routers in large networks is in common use.<a href="#cite_note-44">[43]</a> Some routers can connect to <a href="Data_service_unit" title="Data service unit">Data service units</a> for <a href="Digital_Signal_1" title="Digital Signal 1">T1 connections</a><a href="#cite_note-45">[44]</a><a href="#cite_note-46">[45]</a><a href="#cite_note-47">[46]</a> via serial ports.<a href="#cite_note-48">[47]</a><a href="#cite_note-49">[48]</a>

<div class="mw-heading mw-heading3"><h3 id="Access,_core_and_distribution">Access, core and distribution</h3></div>

The <a href="Hierarchical_internetworking_model" title="Hierarchical internetworking model">hierarchical internetworking model</a> divides <a href="Enterprise_network" class="mw-redirect" title="Enterprise network">enterprise networks</a> into three layers: core, distribution, and access.

Access routers, including <a href="Small_office/home_office" title="Small office/home office">small office/home office</a> (SOHO) models, are located at home and customer sites such as branch offices that do not need <a href="Hierarchical_routing" title="Hierarchical routing">hierarchical routing</a> of their own. Typically, they are optimized for low cost. Some SOHO routers are capable of running alternative free Linux-based firmware like <a href="Tomato_(firmware)" title="Tomato (firmware)">Tomato</a>, <a href="OpenWrt" title="OpenWrt">OpenWrt</a>, or <a href="DD-WRT" title="DD-WRT">DD-WRT</a>.<a href="#cite_note-50">[49]</a>

Distribution routers aggregate traffic from multiple access routers. Distribution routers are often responsible for enforcing quality of service across a <a href="Wide_area_network" title="Wide area network">wide area network</a> (WAN), so they may have considerable memory installed, multiple WAN interface connections, and substantial onboard data processing routines. They may also provide connectivity to groups of file servers or other external networks.<a href="#cite_note-51">[50]</a>

In enterprises, a <a href="Core_router" title="Core router">core router</a> may provide a <a href="Collapsed_backbone" class="mw-redirect" title="Collapsed backbone">collapsed backbone</a> interconnecting the distribution tier routers from multiple buildings of a campus, or large enterprise locations. They tend to be optimized for high bandwidth but lack some of the features of edge routers.<a href="#cite_note-52">[51]</a>

<div class="mw-heading mw-heading3"><h3 id="Security">Security</h3></div>

External networks must be carefully considered as part of the overall security strategy of the local network. A router may include a <a href="Firewall_(computing)" title="Firewall (computing)">firewall</a>, <a href="VPN" class="mw-redirect" title="VPN">VPN</a> handling, and other security functions, or they may be handled by separate devices. Routers also commonly perform <a href="Network_address_translation" title="Network address translation">network address translation</a> which restricts connections initiated from external connections but is not recognized as a security feature by all experts.<a href="#cite_note-53">[52]</a> Some experts argue that <a href="Open-source_software" title="Open-source software">open source</a> routers are more secure and reliable than <a href="Closed_source" class="mw-redirect" title="Closed source">closed source</a> routers because errors and potentially exploitable <a href="Vulnerability_(computing)" class="mw-redirect" title="Vulnerability (computing)">vulnerabilities</a> are more likely to be discovered and addressed in an open-source environment.<a href="#cite_note-54">[53]</a><a href="#cite_note-55">[54]</a>

<div class="mw-heading mw-heading3"><h3 id="Routing_different_networks">Routing different networks</h3></div>

Routers are also often distinguished on the basis of the network in which they operate. A router in a <a href="Local_area_network" title="Local area network">local area network</a> (LAN) of a single organization is called an interior router. A router that is operated in the <a href="Internet" title="Internet">Internet</a> backbone is described as exterior router. While a router that connects a LAN with the Internet or a <a href="Wide_area_network" title="Wide area network">wide area network</a> (WAN) is called a border router, or <a href="Gateway_router" class="mw-redirect" title="Gateway router">gateway router</a>.<a href="#cite_note-56">[55]</a>

<div class="mw-heading mw-heading3"><h3 id="Internet_connectivity_and_internal_use">Internet connectivity and internal use</h3></div>

Routers intended for ISP and major enterprise connectivity usually exchange routing information using the <a href="Border_Gateway_Protocol" title="Border Gateway Protocol">Border Gateway Protocol</a> (BGP). <style data-mw-deduplicate="TemplateStyles:r1238218222">

/* start https://en.wikipedia.org/ */

.mw-parser-output cite.citation{font-style:inherit;word-wrap:break-word}.mw-parser-output .citation q{quotes:"\"""\"""'""'"}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}.mw-parser-output .id-lock-free.id-lock-free a{background:url("./mw/Lock-green.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-limited.id-lock-limited a,.mw-parser-output .id-lock-registration.id-lock-registration a{background:url("./mw/Lock-gray-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-subscription.id-lock-subscription a{background:url("./mw/Lock-red-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .cs1-ws-icon a{background:url("./mw/Wikisource-logo.svg")right 0.1em center/12px no-repeat}body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-free a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-limited a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-registration a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-subscription a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .cs1-ws-icon a{background-size:contain;padding:0 1em 0 0}.mw-parser-output .cs1-code{color:inherit;background:inherit;border:none;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;color:var(--color-error,#d33)}.mw-parser-output .cs1-visible-error{color:var(--color-error,#d33)}.mw-parser-output .cs1-maint{display:none;color:#085;margin-left:0.3em}.mw-parser-output .cs1-kern-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right{padding-right:0.2em}.mw-parser-output .citation .mw-selflink{font-weight:inherit}@media screen{.mw-parser-output .cs1-format{font-size:95%}html.skin-theme-clientpref-night .mw-parser-output .cs1-maint{color:#18911f}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .cs1-maint{color:#18911f}}

/* end https://en.wikipedia.org/ */

</style><a href="RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc4098">4098</a> defines the types of BGP routers according to their functions:<a href="#cite_note-RFC_4098-57">[56]</a>

<ul><li>Edge router or inter-AS border router: Placed at the edge of an ISP network, where the router is used to peer with the upstream IP transit providers, bilateral peers through <a href="IXP" class="mw-redirect" title="IXP">IXP</a>, private peering (or even settlement-free peering) through <a href="Private_Network_Interconnect" class="mw-redirect" title="Private Network Interconnect">Private Network Interconnect</a> (PNI) via the extensive use of <a href="Exterior_Border_Gateway_Protocol" class="mw-redirect" title="Exterior Border Gateway Protocol">Exterior Border Gateway Protocol</a> (eBGP).<a href="#cite_note-58">[57]</a></li>

<li>Provider Router (P): A Provider router is also called a transit-router, it sits in an MPLS network and is responsible for establishing label-switched paths between the PE routers.<a href="#cite_note-:0-59">[58]</a></li>

<li>Provider edge router (PE): An MPLS-specific router in the network's access layer that interconnects with customer edge routers to provide layer 2 or layer 3 VPN services.<a href="#cite_note-:0-59">[58]</a></li>

<li>Customer edge router (CE): Located at the edge of the subscriber's network, it interconnects with the PE router for L2VPN services, or direct layer 3 IP hand-off in the case of <a href="Dedicated_line" title="Dedicated line">Dedicated Internet Access</a>, if IP Transit services are provided through an MPLS core, the CE peers with the PE using eBGP with the public ASNs of each respective network. In the case of L3VPN services the CE can exchange routes with the PE using eBGP. It is commonly used in both service provider and enterprise or <a href="Data_center" title="Data center">data center</a> organizations.<a href="#cite_note-:0-59">[58]</a></li>

<li><a href="Core_router" title="Core router">Core router</a>: Resides within an Autonomous System as a backbone to carry traffic between edge routers.<a href="#cite_note-60">[59]</a></li>

<li>Within an ISP: In the ISP's autonomous system, a router uses internal BGP to communicate with other ISP edge routers, other <a href="Intranet" title="Intranet">intranet</a> core routers, or the ISP's intranet provider border routers.</li>

<li>Internet backbone: The Internet no longer has a clearly identifiable backbone, unlike its predecessor networks. See <a href="Default-free_zone" title="Default-free zone">default-free zone</a> (DFZ). The major ISPs' system routers make up what could be considered to be the current Internet backbone core.<a href="#cite_note-61">[60]</a> ISPs operate all four types of the BGP routers described here. An ISP core router is used to interconnect its edge and border routers. Core routers may also have specialized functions in <a href="Virtual_private_network" title="Virtual private network">virtual private networks</a> based on a combination of BGP and <a href="Multiprotocol_Label_Switching" title="Multiprotocol Label Switching">Multiprotocol Label Switching</a> protocols.<a href="#cite_note-62">[61]</a></li>

<li>Port forwarding: In some networks, that rely on legacy IPv4 and NAT, routers (often labeled as NAT boxes) are also used for <a href="Port_forwarding" title="Port forwarding">port forwarding</a> configuration between RFC1918 address space and their publicly assigned IPv4 address.<a href="#cite_note-port-43">[42]</a></li>

<li>Voice, data, fax, and video processing routers: Commonly referred to as <a href="Access_servers" class="mw-redirect" title="Access servers">access servers</a> or <a href="Gateway_(telecommunications)" title="Gateway (telecommunications)">gateways</a>, these devices are used to route and process voice, data, video and fax traffic on the Internet. Since 2005, most long-distance phone calls have been processed as <a href="Internet_Protocol" title="Internet Protocol">IP</a> traffic (<a href="VOIP" class="mw-redirect" title="VOIP">VOIP</a>) through a voice gateway. Use of access server-type routers expanded with the advent of the Internet, first with dial-up access and another resurgence with voice phone service.</li>

<li>Larger networks commonly use <a href="Multilayer_switch" title="Multilayer switch">multilayer switches</a>, with layer-3 devices being used to simply interconnect multiple subnets within the same security zone, and higher-layer switches when <a href="Firewall_(computing)" title="Firewall (computing)">filtering</a>, <a href="Network_address_translation" title="Network address translation">translation</a>, <a href="Load_balancing_(computing)" title="Load balancing (computing)">load balancing</a>, or other higher-level functions are required, especially between zones.</li></ul>

<div class="mw-heading mw-heading3"><h3 id="Wi-Fi_routers">Wi-Fi routers</h3></div>

<div role="note" class="hatnote navigation-not-searchable">Main article: <a href="Wireless_router" title="Wireless router">Wireless router</a></div>

Wi-Fi routers combine the functions of a router with those of a <a href="Wireless_access_point" title="Wireless access point">wireless access point</a>. They are typically devices with a small form factor, operating on the standard electric power supply for residential use. Connected to the Internet as offered by an <a href="Internet_service_provider" title="Internet service provider">Internet service provider</a>, they provide Internet access through a <a href="Wireless_network" title="Wireless network">wireless network</a> for home or office use.

<div class="mw-heading mw-heading2"><h2 id="Forwarding">Forwarding</h2></div>

<div role="note" class="hatnote navigation-not-searchable">Further information: <a href="Routing" title="Routing">Routing</a> and <a href="IP_routing" title="IP routing">IP routing</a></div>

The main purpose of a router is to connect multiple networks and forward packets destined either for directly attached networks or more remote networks. A router is considered a <a href="Layer-3" class="mw-redirect" title="Layer-3">layer-3</a> device because its primary forwarding decision is based on the information in the layer-3 IP packet, specifically the destination IP address. When a router receives a packet, it searches its routing table to find the best match between the destination IP address of the packet and one of the addresses in the routing table. Once a match is found, the packet is encapsulated in the <a href="Layer-2" class="mw-redirect" title="Layer-2">layer-2</a> data link frame for the outgoing interface indicated in the table entry. A router typically does not look into the packet payload,<a href="#cite_note-63">[62]</a> but only at the layer-3 addresses to make a forwarding decision, plus optionally other information in the header for hints on, for example, <a href="Quality_of_service" title="Quality of service">quality of service</a> (QoS). For pure IP forwarding, a router is designed to minimize the <a href="State_(computer_science)" title="State (computer science)">state</a> information associated with individual packets.<a href="#cite_note-64">[63]</a> Once a packet is forwarded, the router does not retain any historical information about the packet.<a href="#cite_note-65">[b]</a>

The routing table itself can contain information derived from a variety of sources, such as a <a href="Default_route" title="Default route">default</a> or <a href="Static_route" class="mw-redirect" title="Static route">static routes</a> that are configured manually, or dynamic entries from <a href="Routing_protocol" title="Routing protocol">routing protocols</a> where the router learns routes from other routers. A default route is one that is used to route all traffic whose destination does not otherwise appear in the routing table; it is common – even necessary – in small networks, such as a home or small business where the default route simply sends all non-local traffic to the <a href="Internet_service_provider" title="Internet service provider">Internet service provider</a>. The default route can be manually configured (as a static route); learned by dynamic routing protocols; or be obtained by <a href="DHCP" class="mw-redirect" title="DHCP">DHCP</a>.<a href="#cite_note-66">[c]</a><a href="#cite_note-67">[64]</a>

A router can run more than one routing protocol at a time, particularly if it serves as an autonomous system border router between parts of a network that run different routing protocols; if it does so, then redistribution may be used (usually selectively) to share information between the different protocols running on the same router.<a href="#cite_note-68">[65]</a>

Besides deciding to which interface a packet is forwarded, which is handled primarily via the routing table, a router also has to manage congestion when packets arrive at a rate higher than the router can process. Three policies commonly used are <a href="Tail_drop" title="Tail drop">tail drop</a>, <a href="Random_early_detection" title="Random early detection">random early detection</a> (RED), and <a href="Weighted_random_early_detection" title="Weighted random early detection">weighted random early detection</a> (WRED). Tail drop is the simplest and most easily implemented: the router simply drops new incoming packets once buffer space in the router is exhausted. RED probabilistically drops datagrams early when the queue exceeds a pre-configured portion of the buffer, until reaching a pre-determined maximum, when it drops all incoming packets, thus reverting to tail drop. WRED can be configured to drop packets more readily dependent on the type of traffic.

Another function a router performs is <a href="Traffic_classification" title="Traffic classification">traffic classification</a> and deciding which packet should be processed first. This is managed through <a href="Quality_of_service" title="Quality of service">QoS</a>, which is critical when <a href="Voice_over_IP" title="Voice over IP">Voice over IP</a> is deployed, so as not to introduce excessive <a href="Latency_(audio)" title="Latency (audio)">latency</a>.<a href="#cite_note-69">[66]</a>

Yet another function a router performs is called <a href="Policy-based_routing" title="Policy-based routing">policy-based routing</a> where special rules are constructed to override the rules derived from the routing table when a packet forwarding decision is made.<a href="#cite_note-70">[67]</a>

Some of the functions may be performed through an <a href="Application-specific_integrated_circuit" title="Application-specific integrated circuit">application-specific integrated circuit</a> (ASIC) to avoid the overhead of scheduling CPU time to process the packets. Others may have to be performed through the CPU as these packets need special attention that cannot be handled by an ASIC.<a href="#cite_note-71">[68]</a>

<ul><li><a href="Mobile_broadband_modem" title="Mobile broadband modem">Mobile broadband modem</a></li>

<li><a href="Modem" title="Modem">Modem</a></li>

<li><a href="Residential_gateway" title="Residential gateway">Residential gateway</a></li>

<li><a href="Switch_virtual_interface" title="Switch virtual interface">Switch virtual interface</a></li>

<li><a href="Wireless_router" title="Wireless router">Wireless router</a></li></ul>

<div class="mw-heading mw-heading2"><h2 id="Notes">Notes</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .reflist{margin-bottom:0.5em;list-style-type:decimal}@media screen{.mw-parser-output .reflist{font-size:90%}}.mw-parser-output .reflist .references{font-size:100%;margin-bottom:0;list-style-type:inherit}.mw-parser-output .reflist-columns-2{column-width:30em}.mw-parser-output .reflist-columns-3{column-width:25em}.mw-parser-output .reflist-columns{margin-top:0.3em}.mw-parser-output .reflist-columns ol{margin-top:0}.mw-parser-output .reflist-columns li{page-break-inside:avoid;break-inside:avoid-column}.mw-parser-output .reflist-upper-alpha{list-style-type:upper-alpha}.mw-parser-output .reflist-upper-roman{list-style-type:upper-roman}.mw-parser-output .reflist-lower-alpha{list-style-type:lower-alpha}.mw-parser-output .reflist-lower-greek{list-style-type:lower-greek}.mw-parser-output .reflist-lower-roman{list-style-type:lower-roman}

/* end https://en.wikipedia.org/ */

</style><div class="reflist reflist-lower-alpha">

<li id="cite_note-2"><a href="#cite_ref-2">^</a> Pronounced /ˈruːtər/ in <a href="British_English" title="British English">British English</a>, /ˈraʊtər/ in <a href="American_English" title="American English">American</a> and <a href="Australian_English" title="Australian English">Australian English</a>.<a href="#cite_note-1">[1]</a>

</li>

<li id="cite_note-65"><a href="#cite_ref-65">^</a> In some router implementations, the forwarding action can increment a counter associated with the routing table entry for the collection of statistical data.

</li>

<li id="cite_note-66"><a href="#cite_ref-66">^</a> A router can serve as a DHCP client or as a DHCP server.

</li>

</ol></div></div>

<div class="mw-heading mw-heading2"><h2 id="References">References</h2></div>

<li id="cite_note-1"><a href="#cite_ref-1">^</a> <cite id="CITEREFReference-OED-router" class="citation encyclopaedia cs1"><a rel="nofollow" class="external text" href="https://www.oed.com/search/dictionary/?q=router">"router"</a>. <a href="Oxford_English_Dictionary" title="Oxford English Dictionary">Oxford English Dictionary</a> (Online ed.). <a href="Oxford_University_Press" title="Oxford University Press">Oxford University Press</a>.</cite> (Subscription or <a rel="nofollow" class="external text" href="https://www.oed.com/public/login/loggingin#withyourlibrary">participating institution membership</a> required.)

</li>

<li id="cite_note-3"><a href="#cite_ref-3">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20220705091357/http://cisco.num.edu.mn/CCNA_R&S1/course/module6/6.3.1.1/6.3.1.1.html">"A Router is a Computer"</a>. Cisco Network Academy. Archived from <a rel="nofollow" class="external text" href="http://cisco.num.edu.mn/CCNA_R&S1/course/module6/6.3.1.1/6.3.1.1.html">the original</a> on 2022-07-05.</cite>

</li>

<li id="cite_note-Medhi-4"><a href="#cite_ref-Medhi_4-0">^</a> <cite id="CITEREFMedhiRamasamy2007" class="citation book cs1">Medhi, Deepankar; Ramasamy, Karthik (2007). <a rel="nofollow" class="external text" href="https://books.google.com/books?id=IM-Y2W0RIF0C&dq=%22router+is+a+specialized+computer%22&pg=PA19">Network Routing: Algorithms, Protocols, and Architectures</a>. Elsevier. p. 19. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>9780120885886</bdi>.</cite>

</li>

<li id="cite_note-Kundu-5"><a href="#cite_ref-Kundu_5-0">^</a> <cite id="CITEREFKundu2009" class="citation book cs1">Kundu, Sudakshina (2009). <a rel="nofollow" class="external text" href="https://books.google.com/books?id=OMoHmEQHosAC&q=router%20is%20a">Fundamentals of Computer Networks, 2nd Ed</a>. New Delhi: PHI Learning. pp. 85–86, 124. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>9788120334526</bdi>.</cite>

</li>

<li id="cite_note-6"><a href="#cite_ref-6">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://www.tcpipguide.com/free/t_OverviewOfKeyRoutingProtocolConceptsArchitecturesP.htm">"Overview Of Key Routing Protocol Concepts: Architectures, Protocol Types, Algorithms and Metrics"</a>. Tcpipguide.com. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20101220111345/http://tcpipguide.com/free/t_OverviewOfKeyRoutingProtocolConceptsArchitecturesP.htm">Archived</a> from the original on 20 December 2010. Retrieved 15 January 2011.</cite>

</li>

<li id="cite_note-7"><a href="#cite_ref-7">^</a> <cite id="CITEREFDavies1966" class="citation web cs1">Davies, D. W. (1966). <a rel="nofollow" class="external text" href="https://www.dcs.gla.ac.uk/~wpc/grcs/Davies05.pdf">"Proposal for a Digital Communication Network"</a> (PDF).</cite>

</li>

<li id="cite_note-8"><a href="#cite_ref-8">^</a> <cite id="CITEREFRoberts1995" class="citation web cs1">Roberts, Dr. Lawrence G. (May 1995). <a rel="nofollow" class="external text" href="http://www.packet.cc/files/arpanet-computernet.html">"The ARPANET & Computer Networks"</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20160324032800/http://www.packet.cc/files/arpanet-computernet.html">Archived</a> from the original on 24 March 2016. Retrieved 13 April 2016. <q>Then in June 1966, Davies wrote a second internal paper, "Proposal for a Digital Communication Network" In which he coined the word packet,- a small sub part of the message the user wants to send, and also introduced the concept of an interface computer to sit between the user equipment and the packet network.</q></cite>

</li>

<li id="cite_note-9"><a href="#cite_ref-9">^</a> <cite id="CITEREFPelkey2007" class="citation book cs1">Pelkey, James (2007). <a rel="nofollow" class="external text" href="http://www.historyofcomputercommunications.info/Individuals/abstracts/donald-davies.html">Entrepreneurial Capitalism & Innovation: A History of Computer Communications 1968 - 1988</a>. Retrieved 2020-02-18. <q>paper dated June 1966 ... introduced the concept of an "interface computer" to sit between the user equipment and the packet network.</q></cite>

</li>

<li id="cite_note-:2-10"><a href="#cite_ref-:2_10-0">^</a> <cite id="CITEREFPelkey" class="citation web cs1">Pelkey, James. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20221223230647/https://historyofcomputercommunications.info/section/4.7/planning-the-arpanet-1967-1968/">"4.7 Planning the ARPANET: 1967-1968 in Chapter 4 - Networking: Vision and Packet Switching 1959 - 1968"</a>. The History of Computer Communications. Archived from <a rel="nofollow" class="external text" href="https://historyofcomputercommunications.info/section/4.7/planning-the-arpanet-1967-1968/">the original</a> on December 23, 2022. Retrieved May 9, 2023.</cite>

</li>

<li id="cite_note-:22-11"><a href="#cite_ref-:22_11-0">^</a> <cite id="CITEREFJohn_SJosiah_C1986" class="citation journal cs1">John S, Quarterman; Josiah C, Hoskins (1986). <a rel="nofollow" class="external text" href="https://doi.org/10.1145%2F6617.6618">"Notable computer networks"</a>. Communications of the ACM. 29 (10): 932–971. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1145%2F6617.6618">10.1145/6617.6618</a>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:25341056">25341056</a>. <q>The first packet-switching network was implemented at the National Physical Laboratories in the United Kingdom. It was quickly followed by the ARPANET in 1969.</q></cite>

</li>

<li id="cite_note-12"><a href="#cite_ref-12">^</a> <cite id="CITEREFScantlebury2001" class="citation conference cs1">Scantlebury, Roger (2001). <a rel="nofollow" class="external text" href="https://web.archive.org/web/20030807200346/http://www.topquark.co.uk/conf/IAP2001.html">A Brief History of the NPL Network</a>. Symposium of the Institution of Analysts & Programmers 2001. Archived from <a rel="nofollow" class="external text" href="http://www.topquark.co.uk/conf/IAP2001.html">the original</a> on 2003-08-07. Retrieved 2024-06-13. <q>The system first went 'live' early in 1969</q></cite>

</li>

<li id="cite_note-13"><a href="#cite_ref-13">^</a> <cite id="CITEREFHaughney_Dare-Bryan2023" class="citation audio-visual cs1">Haughney Dare-Bryan, Christine (June 22, 2023). <a rel="nofollow" class="external text" href="https://www.inc.com/computerfreaks">Computer Freaks</a> (Podcast). Chapter Two: In the Air. Inc. Magazine. 35:55 minutes in. <q>Leonard Kleinrock: Donald Davies ... did make a single node packet switch before ARPA did</q></cite>

</li>

<li id="cite_note-C._Hempstead,_W._Worthington-14"><a href="#cite_ref-C._Hempstead,_W._Worthington_14-0">^</a> <cite id="CITEREFHempsteadWorthington2005" class="citation book cs1">Hempstead, C.; Worthington, W., eds. (2005). <a rel="nofollow" class="external text" href="https://archive.org/details/EncyclopediaOf20thCenturyTechnologyAZMalestrom/page/n621/mode/2up?q=packet+switching">Encyclopedia of 20th-Century Technology</a>. <a href="Routledge" title="Routledge">Routledge</a>. pp. 573–5. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>9781135455514</bdi>. Retrieved 2015-08-15.</cite>

</li>

<li id="cite_note-15"><a href="#cite_ref-15">^</a> Davies, Shanks, Heart, Barker, Despres, Detwiler and Riml, "Report of Subgroup 1 on Communication System", INWG Note No. 1.

</li>

<li id="cite_note-16"><a href="#cite_ref-16">^</a> <cite id="CITEREFEdmondson-Yurkanan2007" class="citation journal cs1">Edmondson-Yurkanan, Chris (2007). <a rel="nofollow" class="external text" href="https://dl.acm.org/doi/10.1145/1230819.1230840">"SIGCOMM's archaeological journey into networking's past"</a>. Communications of the ACM. 50 (5): 63–68. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1145%2F1230819.1230840">10.1145/1230819.1230840</a>. <a href="ISSN_(identifier)" class="mw-redirect" title="ISSN (identifier)">ISSN</a> <a rel="nofollow" class="external text" href="https://search.worldcat.org/issn/0001-0782">0001-0782</a>. <q>INWG#1: Report of Subgroup 1 on Communication System Requirements by Davies, Shanks, Heart, Barker, Despres, Detwiler, and Riml. They wrote: "It was agreed that interworkingbetween packet switching networks should not add complications to the hosts, considering that networks will probably be different and thus gateways between networks will be required. These gateways should be as uncomplicated as possible, whilst allowing as much freedom as possible for the design of individual networks". INWG#1 clarified that gateways and simplicity were accepted concepts when INWG was formed.</q></cite>

</li>

<li id="cite_note-:5-17"><a href="#cite_ref-:5_17-0">^</a> <cite id="CITEREFDaviesBartlettScantleburyWilkinson1967" class="citation conference cs1">Davies, Donald; Bartlett, Keith; Scantlebury, Roger; Wilkinson, Peter (October 1967). <a rel="nofollow" class="external text" href="https://people.mpi-sws.org/~gummadi/teaching/sp07/sys_seminar/how_did_erope_blow_this_vision.pdf">A Digital Communication Network for Computers Giving Rapid Response at remote Terminals</a> (PDF). ACM Symposium on Operating Systems Principles. <a rel="nofollow" class="external text" href="https://ghostarchive.org/archive/20221010/https://people.mpi-sws.org/~gummadi/teaching/sp07/sys_seminar/how_did_erope_blow_this_vision.pdf">Archived</a> (PDF) from the original on 2022-10-10. Retrieved 2020-09-15. <q>It is thought that all users of the network will provide themselves with some kind of error control and that without difficulty this could be made to show up a missing packet. Because of this, loss of packets, if it is sufficiently rare, can be tolerated.</q></cite>

</li>

<li id="cite_note-Pelkey8.3-18"><a href="#cite_ref-Pelkey8.3_18-0">^</a> <cite id="CITEREFPelkey" class="citation book cs1">Pelkey, James. <a rel="nofollow" class="external text" href="https://historyofcomputercommunications.info/section/8.3/CYCLADES-Network-and-Louis-Pouzin-1971-1972/">"8.3 CYCLADES Network and Louis Pouzin 1971–1972"</a>. Entrepreneurial Capitalism and Innovation: A History of Computer Communications 1968–1988. <q>The inspiration for datagrams had two sources. One was Donald Davies' studies. He had done some simulation of datagram networks, although he had not built any, and it looked technically viable. The second inspiration was I like things simple. I didn't see any real technical motivation to overlay two levels of end-to-end protocols. I thought one was enough.</q></cite>

</li>

<li id="cite_note-:3-19"><a href="#cite_ref-:3_19-0">^</a> <cite id="CITEREFRussellSchafer2014" class="citation journal cs1">Russell, Andrew L.; Schafer, Valérie (2014). <a rel="nofollow" class="external text" href="https://www.jstor.org/stable/24468474">"In the Shadow of ARPANET and Internet: Louis Pouzin and the Cyclades Network in the 1970s"</a>. Technology and Culture. 55 (4): 880–907. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1353%2Ftech.2014.0096">10.1353/tech.2014.0096</a>. <a href="ISSN_(identifier)" class="mw-redirect" title="ISSN (identifier)">ISSN</a> <a rel="nofollow" class="external text" href="https://search.worldcat.org/issn/0040-165X">0040-165X</a>. <a href="JSTOR_(identifier)" class="mw-redirect" title="JSTOR (identifier)">JSTOR</a> <a rel="nofollow" class="external text" href="https://www.jstor.org/stable/24468474">24468474</a>.</cite>

</li>

<li id="cite_note-20"><a href="#cite_ref-20">^</a> <cite id="CITEREFGreen2010" class="citation book cs1">Green, Lelia (2010). <a rel="nofollow" class="external text" href="https://www.worldcat.org/title/504280762">The internet: an introduction to new media</a>. Berg new media series. Berg. p. 31. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-1-84788-299-8</bdi>. <a href="OCLC_(identifier)" class="mw-redirect" title="OCLC (identifier)">OCLC</a> <a rel="nofollow" class="external text" href="https://search.worldcat.org/oclc/504280762">504280762</a>. <q>The original ARPANET design had made data integrity part of the IMP's store-and-forward role, but Cyclades end-to-end protocol greatly simplified the packet switching operations of the network. ... The idea was to adopt several principles from Cyclades and invert the ARPANET model to minimise international differences.</q></cite>

</li>

<li id="cite_note-Bennett2009-21"><a href="#cite_ref-Bennett2009_21-0">^</a> <cite id="CITEREFBennett2009" class="citation web cs1">Bennett, Richard (September 2009). <a rel="nofollow" class="external text" href="https://www.itif.org/files/2009-designed-for-change.pdf">"Designed for Change: End-to-End Arguments, Internet Innovation, and the Net Neutrality Debate"</a> (PDF). Information Technology and Innovation Foundation. pp. 7, 9, 11. Retrieved 11 September 2017. <q>Two significant packet networks preceded the TCP/IP Internet: ARPANET and CYCLADES. The designers of the Internet borrowed heavily from these systems, especially CYCLADES ... The first end-to-end research network was CYCLADES, designed by Louis Pouzin at IRIA in France with the support of BBN's Dave Walden and Alex McKenzie and deployed beginning in 1972.</q></cite>

</li>

<li id="cite_note-22"><a href="#cite_ref-22">^</a> <cite id="CITEREFTaylor2008" class="citation cs2 cs1-prop-long-vol">Taylor, Bob (October 11, 2008), <a rel="nofollow" class="external text" href="http://archive.computerhistory.org/resources/access/text/2013/05/102702015-05-01-acc.pdf">"Oral History of Robert (Bob) W. Taylor"</a> (PDF), Computer History Museum Archive, CHM Reference number: X5059.2009: 28</cite>

</li>

<li id="cite_note-23"><a href="#cite_ref-23">^</a> David Boggs, John Shoch, Edward Taft, Robert Metcalfe, <a rel="nofollow" class="external text" href="https://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=1094684">"Pup: An Internetwork Architecture"</a>, IEEE Transactions on Communications, Volume 28, Issue 4, April 1980, pp. 612- 624.

</li>

<li id="cite_note-Cerf-1974-24"><a href="#cite_ref-Cerf-1974_24-0">^</a> <cite id="CITEREFCerfKahn1974" class="citation journal cs1">Cerf, V.; Kahn, R. (1974). <a rel="nofollow" class="external text" href="https://www.cs.princeton.edu/courses/archive/fall06/cos561/papers/cerf74.pdf">"A Protocol for Packet Network Intercommunication"</a> (PDF). IEEE Transactions on Communications. 22 (5): 637–648. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1109%2FTCOM.1974.1092259">10.1109/TCOM.1974.1092259</a>. <a href="ISSN_(identifier)" class="mw-redirect" title="ISSN (identifier)">ISSN</a> <a rel="nofollow" class="external text" href="https://search.worldcat.org/issn/1558-0857">1558-0857</a>. <q>The authors wish to thank a number of colleagues for helpful comments during early discussions of international network protocols, especially R. Metcalfe, R. Scantlebury, D. Walden, and H. Zimmerman; D. Davies and L. Pouzin who constructively commented on the fragmentation and accounting issues; and S. Crocker who commented on the creation and destruction of associations.</q></cite>

</li>

<li id="cite_note-25"><a href="#cite_ref-25">^</a> <cite class="citation cs1"><a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc1087">Ethics and the Internet</a>. January 1989. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC1087">10.17487/RFC1087</a>. <a href="Request_for_Comments" title="Request for Comments">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc1087">1087</a>. <q>At great human and economic cost, resources drawn from the U.S. Government, industry and the academic community have been assembled into a collection of interconnected networks called the Internet.</q></cite>

</li>

<li id="cite_note-26"><a href="#cite_ref-26">^</a> <cite class="citation cs1"><a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc2555">30 Years of RFCs</a>. 7 April 1999. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC2555">10.17487/RFC2555</a>. <a href="Request_for_Comments" title="Request for Comments">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc2555">2555</a>. <q>Reflections - Joyce K. Reynolds: A very long time ago when I was dabbling in IP network number and protocol parameter assignments with Jon Postel, gateways were still "dumb", the Exterior Gateway Protocol (EGP) was in its infancy and TOPS-20 was in its heyday.</q></cite>

</li>

<li id="cite_note-:9-27"><a href="#cite_ref-:9_27-0">^</a> <cite id="CITEREFKirstein1999" class="citation journal cs1">Kirstein, P.T. (1999). "Early experiences with the Arpanet and Internet in the United Kingdom". IEEE Annals of the History of Computing. 21 (1): 38–44. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1109%2F85.759368">10.1109/85.759368</a>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:1558618">1558618</a>.</cite>

</li>

<li id="cite_note-28"><a href="#cite_ref-28">^</a> <cite class="citation cs1"><a rel="nofollow" class="external text" href="https://www.rfc-editor.org/ien/ien190.txt">Routing and Access Control in UK to US Services</a>. IEN 190.</cite>

</li>

<li id="cite_note-29"><a href="#cite_ref-29">^</a> <cite id="CITEREFKirstein1984" class="citation journal cs1">Kirstein, P. T. (December 1984). <a rel="nofollow" class="external text" href="https://discovery.ucl.ac.uk/id/eprint/10076375/1/pub-102-D.pdf">"The University College London International Computer Communications Interconnection Service"</a> (PDF). Internal Working Paper.</cite>

</li>

<li id="cite_note-30"><a href="#cite_ref-30">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.internethalloffame.org/inductee/virginia-travers/">"Virginia Travers"</a>. Internet Hall of Fame. Retrieved 2024-06-16.</cite>

</li>

<li id="cite_note-31"><a href="#cite_ref-31">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://www.ithistory.org/honor-roll/ms-ginny-strazisar">"Ms. Ginny Strazisar"</a>. IT History Society. 21 December 2015. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20171201034131/http://www.ithistory.org/honor-roll/ms-ginny-strazisar">Archived</a> from the original on 1 December 2017. Retrieved 21 November 2017.</cite>

</li>

<li id="cite_note-32"><a href="#cite_ref-32">^</a> Craig Partridge, S. Blumenthal, <a rel="nofollow" class="external text" href="https://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=1603444">"Data networking at BBN"</a>; IEEE Annals of the History of Computing, Volume 28, Issue 1; January–March 2006.

</li>

<li id="cite_note-33"><a href="#cite_ref-33">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://corporate-awards.ieee.org/wp-content/uploads/internet-rl.pdf">"IEEE INTERNET AWARD RECIPIENTS"</a> (PDF).</cite>

</li>

<li id="cite_note-34"><a href="#cite_ref-34">^</a> <a rel="nofollow" class="external text" href="https://www.pbs.org/cringely/pulpit/1998/pulpit_19981210_000593.html">Valley of the Nerds: Who Really Invented the Multiprotocol Router, and Why Should We Care?</a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20160303172753/http://www.pbs.org/cringely/pulpit/1998/pulpit_19981210_000593.html">Archived</a> 2016-03-03 at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a>, Public Broadcasting Service, Accessed August 11, 2007.

</li>

<li id="cite_note-35"><a href="#cite_ref-35">^</a> <a rel="nofollow" class="external text" href="http://www.networkworld.com/supp/2006/anniversary/032706-routerman.html?t5">Router Man</a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20130605195255/http://www.networkworld.com/supp/2006/anniversary/032706-routerman.html?t5">Archived</a> 2013-06-05 at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a>, NetworkWorld, Accessed June 22, 2007.

</li>

<li id="cite_note-36"><a href="#cite_ref-36">^</a> David D. Clark, "M.I.T. Campus Network Implementation", CCNG-2, Campus Computer Network Group, M.I.T., Cambridge, 1982; pp. 26.

</li>

<li id="cite_note-37"><a href="#cite_ref-37">^</a> Pete Carey, "A Start-Up's True Tale: Often-told story of Cisco's launch leaves out the drama, intrigue", San Jose Mercury News, December 1, 2001.

</li>

<li id="cite_note-38"><a href="#cite_ref-38">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://www.ciscopress.com/articles/article.asp?p=2180210&seqNum=4">"Cisco Networking Academy's Introduction to Routing Dynamically"</a>. Cisco. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20151027133937/http://www.ciscopress.com/articles/article.asp?p=2180210&seqNum=4">Archived</a> from the original on October 27, 2015. Retrieved August 1, 2015.</cite>

</li>

<li id="cite_note-Cisco_2022_u602-39"><a href="#cite_ref-Cisco_2022_u602_39-0">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.cisco.com/c/en/us/products/routers/what-is-routing.html">"What Is Routing?"</a>. Cisco. 2022-04-10. Retrieved 2024-03-25. <q>Routing tables can be created manually and "learned" by software as it observes network traffic, or they can be built according to <a href="Routing_protocols" class="mw-redirect" title="Routing protocols">routing protocols</a>.</q></cite>

</li>

<li id="cite_note-40"><a href="#cite_ref-40">^</a> <cite id="CITEREFH._Khosravi_&_T._Anderson2003" class="citation cs1">H. Khosravi & T. Anderson (November 2003). <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc3654">Requirements for Separation of IP Control and Forwarding</a>. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC3654">10.17487/RFC3654</a>. <a href="Request_for_Comments" title="Request for Comments">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc3654">3654</a>.</cite>

</li>

<li id="cite_note-41"><a href="#cite_ref-41">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://iteagers.com/Computer%20Science/Computer%20Networking/446_Which-networking-component-is-responsible-for-directing-data-between-different-networks">"Which networking component is responsible for directing data between different networks - ITEagers"</a>. ITEagers. Retrieved 2024-02-27.</cite>

</li>

<li id="cite_note-42"><a href="#cite_ref-42">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://my-technet.com/index.php/cisco/setting-up-netflow-on-cisco-routers/">"Setting uo Netflow on Cisco Routers"</a>. MY-Technet.com date unknown. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20110714141500/http://my-technet.com/index.php/cisco/setting-up-netflow-on-cisco-routers/">Archived</a> from the original on 14 July 2011. Retrieved 15 January 2011.</cite>

</li>

<li id="cite_note-port-43">^ <a href="#cite_ref-port_43-0">a</a> <a href="#cite_ref-port_43-1">b</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://social.technet.microsoft.com/wiki/contents/articles/windows-home-server-router-setup.aspx">"Windows Home Server: Router Setup"</a>. Microsoft Technet 14 Aug 2010. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20101222175405/http://social.technet.microsoft.com/wiki/contents/articles/windows-home-server-router-setup.aspx">Archived</a> from the original on 22 December 2010. Retrieved 15 January 2011.</cite>

</li>

<li id="cite_note-44"><a href="#cite_ref-44">^</a> <cite id="CITEREFOppenheimer2004" class="citation book cs1">Oppenheimer, Pr (2004). Top-Down Network Design. Indianapolis: Cisco Press. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-1-58705-152-4</bdi>.</cite>

</li>

<li id="cite_note-45"><a href="#cite_ref-45">^</a> <cite id="CITEREFBeasleyNilkaew2012" class="citation book cs1">Beasley, Jeffrey S.; Nilkaew, Piyasat (5 November 2012). <a rel="nofollow" class="external text" href="https://books.google.com/books?id=SQ2WAAAAQBAJ&dq=data+service+unit+t1&pg=PT89">A Practical Guide to Advanced Networking</a>. Pearson Education. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-13-335400-3</bdi>.</cite>

</li>

<li id="cite_note-46"><a href="#cite_ref-46">^</a> <cite id="CITEREFLawson2001" class="citation book cs1">Lawson, Wayne (8 February 2001). <a rel="nofollow" class="external text" href="https://books.google.com/books?id=tGi5xrjPsKoC&dq=data+service+unit+t1&pg=PA43">Configuring Cisco AVVID</a>. Elsevier. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-08-047673-5</bdi>.</cite>

</li>

<li id="cite_note-47"><a href="#cite_ref-47">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://books.google.com/books?id=aDzmTlX49OQC&dq=data+service+unit+t1&pg=PA63">"Computerworld"</a>. 23 January 1995.</cite>

</li>

<li id="cite_note-48"><a href="#cite_ref-48">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.cisco.com/c/en/us/td/docs/routers/access/interfaces/ic/hardware/installation/guide/ser_hwic.html">"Serial Interface Cards"</a>.</cite>

</li>

<li id="cite_note-49"><a href="#cite_ref-49">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.cisco.com/c/en/us/td/docs/routers/access/interfaces/nm/hardware/installation/guide/ConntSer.html">"Serial Network Modules"</a>.</cite>

</li>

<li id="cite_note-50"><a href="#cite_ref-50">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.examcollection.com/certification-training/network-plus-soho-network-requirements-planning-and-implementation.html">"SOHO Network Requirements Planning and Implementation"</a>. ExamCollection. Retrieved 2021-03-25.</cite>

</li>

<li id="cite_note-51"><a href="#cite_ref-51">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://ispfamily.com/how-do-wifi-extenders-work/">"How Do WiFi Extenders Work? Repeater, Booster, Extender?"</a>. ISP Family. 2021-02-25. Retrieved 2021-03-25.</cite>

</li>

<li id="cite_note-52"><a href="#cite_ref-52">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.ciscopress.com/articles/article.asp?p=2202410&seqNum=4">"Hierarchical Network Design Overview (1.1) > Cisco Networking Academy Connecting Networks Companion Guide: Hierarchical Network Design | Cisco Press"</a>. www.ciscopress.com. Retrieved 2021-03-21.</cite>

</li>

<li id="cite_note-53"><a href="#cite_ref-53">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20141018184244/http://www.safecomputing.umich.edu/protect-personal/download/nat_security.pdf">"Security Considerations Of NAT"</a> (PDF). University of Michigan. Archived from <a rel="nofollow" class="external text" href="http://www.safecomputing.umich.edu/protect-personal/download/nat_security.pdf">the original</a> (PDF) on October 18, 2014.</cite>

</li>

<li id="cite_note-54"><a href="#cite_ref-54">^</a> <cite class="citation pressrelease cs1"><a rel="nofollow" class="external text" href="http://www.businesswire.com/news/home/20151014005564/en">"Global Internet Experts Reveal Plan for More Secure, Reliable Wi-Fi Routers - and Internet"</a> (Press release). 14 October 2015. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20151020003515/http://www.businesswire.com/news/home/20151014005564/en">Archived</a> from the original on 2015-10-20.</cite>

</li>

<li id="cite_note-55"><a href="#cite_ref-55">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.govtech.com/security/Is-Open-Source-Software-More-Secure.html">"Is Open Source Software More Secure than Proprietary Products?"</a>. GovTech. 2010-07-26. Retrieved 2024-03-30.</cite>

</li>

<li id="cite_note-56"><a href="#cite_ref-56">^</a> <cite id="CITEREFTamara_Dean2009" class="citation book cs1">Tamara Dean (2009). Network+ Guide to Networks. Cengage Learning. p. 272. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>9781423902454</bdi>.</cite>

</li>

<li id="cite_note-RFC_4098-57"><a href="#cite_ref-RFC_4098_57-0">^</a> <cite id="CITEREFH._Berkowitz2005" class="citation cs1">H. Berkowitz; et al. (June 2005). <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc4098">Terminology for Benchmarking BGP Device Convergence in the Control Plane</a>. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC4098">10.17487/RFC4098</a>. <a href="Request_for_Comments" title="Request for Comments">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc4098">4098</a>.</cite>

</li>

<li id="cite_note-58"><a href="#cite_ref-58">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://iteagers.com/Computer%20Science/Computer%20Networking/21274_What-is-the-primary-role-of-a-router-placed-at-the-edge-of-an-ISP-network-engaging-in-peering-with-upstream-IP-transit-providers-through-eBGP">"What is the primary role of a router placed at the edge of an ISP network engaging in peering with upstream IP transit providers through eBGP - ITEagers"</a>. ITEagers. Retrieved 2024-02-27.</cite>

</li>

<li id="cite_note-:0-59">^ <a href="#cite_ref-:0_59-0">a</a> <a href="#cite_ref-:0_59-1">b</a> <a href="#cite_ref-:0_59-2">c</a> <cite id="CITEREFRekhterRosen2006" class="citation report cs1">Rekhter, Yakov; Rosen, Eric C. (February 2006). <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/rfc4364/">BGP/MPLS IP Virtual Private Networks (VPNs)</a> (Report). Internet Engineering Task Force.</cite>

</li>

<li id="cite_note-60"><a href="#cite_ref-60">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://www.juniper.net/techpubs/qrc/m160-qrc.pdf">"M160 Internet Backbone Router"</a> (PDF). Juniper Networks. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20110920213215/http://www.juniper.net/techpubs/qrc/m160-qrc.pdf">Archived</a> (PDF) from the original on 20 September 2011. Retrieved 15 January 2011.</cite>

</li>

<li id="cite_note-61"><a href="#cite_ref-61">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://www.telecomsportal.com/Assets_papers/Routers_&_Netman/Ironbridge_Virt_Bbone_Route.pdf">"Virtual Backbone Routers"</a> (PDF). IronBridge Networks, Inc. September, 2000. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20110716203325/http://www.telecomsportal.com/Assets_papers/Routers_%26_Netman/Ironbridge_Virt_Bbone_Route.pdf">Archived</a> (PDF) from the original on 16 July 2011. Retrieved 15 January 2011.</cite>

</li>

<li id="cite_note-62"><a href="#cite_ref-62">^</a> <cite id="CITEREFE._RosenY._Rekhter2004" class="citation cs1">E. Rosen; Y. Rekhter (April 2004). BGP/MPLS VPNs.</cite>

</li>

<li id="cite_note-63"><a href="#cite_ref-63">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://docs.oracle.com/cd/E23823_01/html/816-4554/gcvjj.html">"Packet Forwarding and Routing on IPv4 Networks - System Administration Guide: IP Services"</a>. docs.oracle.com. Retrieved 2021-03-25.</cite>

</li>

<li id="cite_note-64"><a href="#cite_ref-64">^</a> <cite id="CITEREFRoberts2003" class="citation web cs1">Roberts, Lawrence (22 July 2003). <a rel="nofollow" class="external text" href="http://www.packet.cc/files/FlowPaper/NextGenerationofIP-FlowRouting.htm">"The Next Generation of IP - Flow Routing"</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20150404030549/http://www.packet.cc/files/FlowPaper/NextGenerationofIP-FlowRouting.htm">Archived</a> from the original on 4 April 2015. Retrieved 22 February 2015.</cite>

</li>

<li id="cite_note-67"><a href="#cite_ref-67">^</a> <cite id="CITEREFDavid_Davis2007" class="citation web cs1">David Davis (April 19, 2007). <a rel="nofollow" class="external text" href="https://web.archive.org/web/20140625042508/http://www.techrepublic.com/article/cisco-administration-101-what-you-need-to-know-about-default-routes/">"Cisco administration 101: What you need to know about default routes"</a>. Archived from the original on June 25, 2014. Retrieved June 5, 2014.</cite><code class="cs1-code">{{cite web}}</code>: CS1 maint: bot: original URL status unknown (link)

</li>

<li id="cite_note-68"><a href="#cite_ref-68">^</a> <cite id="CITEREFDiane_Teare2013" class="citation book cs1">Diane Teare (March 2013). Implementing Cisco IP Routing (ROUTE): Foundation Learning Guide. <a href="Cisco_Press" title="Cisco Press">Cisco Press</a>. pp. 330–334.</cite>

</li>

<li id="cite_note-69"><a href="#cite_ref-69">^</a> <cite id="CITEREFDonahue2007" class="citation book cs1">Donahue, Gary A. (2007-06-21). <a rel="nofollow" class="external text" href="https://books.google.com/books?id=VqebAgAAQBAJ&dq=Network+Warrior+Voice+over+IP+is+a+udp&pg=PA419">Network Warrior</a>. "O'Reilly Media, Inc.". <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-596-10151-0</bdi>.</cite>

</li>

<li id="cite_note-70"><a href="#cite_ref-70">^</a> <cite id="CITEREFDiane_Teare2013" class="citation book cs1">Diane Teare (March 2013). "Chapter 5: Implementing Path Control". Implementing Cisco IP-Routing (ROUTE): Foundation Learning Guide. <a href="Cisco_Press" title="Cisco Press">Cisco Press</a>. pp. 330–334.</cite>

</li>

<li id="cite_note-71"><a href="#cite_ref-71">^</a> <cite id="CITEREFSchudelSmith2007" class="citation book cs1">Schudel, Gregg; Smith, David (2007-12-29). <a rel="nofollow" class="external text" href="https://books.google.com/books?id=DZT7I2U58UoC&dq=that+cannot+be+handled+by+an+ASIC&pg=PT93">Router Security Strategies: Securing IP Network Traffic Planes</a>. Pearson Education. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-13-279673-6</bdi>.</cite>

</li>

</ol></div></div>

<div class="mw-heading mw-heading2"><h2 id="External_links">External links</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .side-box{margin:4px 0;box-sizing:border-box;border:1px solid #aaa;font-size:88%;line-height:1.25em;background-color:var(--background-color-interactive-subtle,#f8f9fa);display:flow-root}.mw-parser-output .infobox .side-box{font-size:100%}.mw-parser-output .side-box-abovebelow,.mw-parser-output .side-box-text{padding:0.25em 0.9em}.mw-parser-output .side-box-image{padding:2px 0 2px 0.9em;text-align:center}.mw-parser-output .side-box-imageright{padding:2px 0.9em 2px 0;text-align:center}@media(min-width:500px){.mw-parser-output .side-box-flex{display:flex;align-items:center}.mw-parser-output .side-box-text{flex:1;min-width:0}}@media(min-width:720px){.mw-parser-output .side-box{width:238px}.mw-parser-output .side-box-right{clear:right;float:right;margin-left:1em}.mw-parser-output .side-box-left{margin-right:1em}}

/* end https://en.wikipedia.org/ */

</style><style data-mw-deduplicate="TemplateStyles:r1237033735">

/* start https://en.wikipedia.org/ */

@media print{body.ns-0 .mw-parser-output .sistersitebox{display:none!important}}@media screen{html.skin-theme-clientpref-night .mw-parser-output .sistersitebox img[src*="Wiktionary-logo-en-v2.svg"]{background-color:white}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .sistersitebox img[src*="Wiktionary-logo-en-v2.svg"]{background-color:white}}

/* end https://en.wikipedia.org/ */

</style><div class="side-box side-box-right sistersitebox"><style data-mw-deduplicate="TemplateStyles:r1126788409">

/* start https://en.wikipedia.org/ */

.mw-parser-output .plainlist ol,.mw-parser-output .plainlist ul{line-height:inherit;list-style:none;margin:0;padding:0}.mw-parser-output .plainlist ol li,.mw-parser-output .plainlist ul li{margin-bottom:0}

/* end https://en.wikipedia.org/ */

</style>

<div class="side-box-text plainlist">Wikimedia Commons has media related to <a href="https://commons.wikimedia.org/wiki/Category:Network_routers" class="extiw external" title="commons:Category:Network routers">Network routers</a>.</div></div>

</div>

<div class="side-box-text plainlist">Wikibooks has a book on the topic of: <a href="https://en.wikibooks.org/wiki/Communication_Networks/Routing" class="extiw external" title="wikibooks:Communication Networks/Routing">Communication Networks/Routing</a></div></div>

</div>

<div class="side-box-text plainlist">Look up <a href="https://en.wiktionary.org/wiki/router" class="extiw external" title="wiktionary:router">router</a> in Wiktionary, the free dictionary.</div></div>

</div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .hlist dl,.mw-parser-output .hlist ol,.mw-parser-output .hlist ul{margin:0;padding:0}.mw-parser-output .hlist dd,.mw-parser-output .hlist dt,.mw-parser-output .hlist li{margin:0;display:inline}.mw-parser-output .hlist.inline,.mw-parser-output .hlist.inline dl,.mw-parser-output .hlist.inline ol,.mw-parser-output .hlist.inline ul,.mw-parser-output .hlist dl dl,.mw-parser-output .hlist dl ol,.mw-parser-output .hlist dl ul,.mw-parser-output .hlist ol dl,.mw-parser-output .hlist ol ol,.mw-parser-output .hlist ol ul,.mw-parser-output .hlist ul dl,.mw-parser-output .hlist ul ol,.mw-parser-output .hlist ul ul{display:inline}.mw-parser-output .hlist .mw-empty-li{display:none}.mw-parser-output .hlist dt::after{content:": "}.mw-parser-output .hlist dd::after,.mw-parser-output .hlist li::after{content:" · ";font-weight:bold}.mw-parser-output .hlist dd:last-child::after,.mw-parser-output .hlist dt:last-child::after,.mw-parser-output .hlist li:last-child::after{content:none}.mw-parser-output .hlist dd dd:first-child::before,.mw-parser-output .hlist dd dt:first-child::before,.mw-parser-output .hlist dd li:first-child::before,.mw-parser-output .hlist dt dd:first-child::before,.mw-parser-output .hlist dt dt:first-child::before,.mw-parser-output .hlist dt li:first-child::before,.mw-parser-output .hlist li dd:first-child::before,.mw-parser-output .hlist li dt:first-child::before,.mw-parser-output .hlist li li:first-child::before{content:" (";font-weight:normal}.mw-parser-output .hlist dd dd:last-child::after,.mw-parser-output .hlist dd dt:last-child::after,.mw-parser-output .hlist dd li:last-child::after,.mw-parser-output .hlist dt dd:last-child::after,.mw-parser-output .hlist dt dt:last-child::after,.mw-parser-output .hlist dt li:last-child::after,.mw-parser-output .hlist li dd:last-child::after,.mw-parser-output .hlist li dt:last-child::after,.mw-parser-output .hlist li li:last-child::after{content:")";font-weight:normal}.mw-parser-output .hlist ol{counter-reset:listitem}.mw-parser-output .hlist ol>li{counter-increment:listitem}.mw-parser-output .hlist ol>li::before{content:" "counter(listitem)"\a0 "}.mw-parser-output .hlist dd ol>li:first-child::before,.mw-parser-output .hlist dt ol>li:first-child::before,.mw-parser-output .hlist li ol>li:first-child::before{content:" ("counter(listitem)"\a0 "}

/* end https://en.wikipedia.org/ */

</style><style data-mw-deduplicate="TemplateStyles:r1236075235">

/* start https://en.wikipedia.org/ */

.mw-parser-output .navbox{box-sizing:border-box;border:1px solid #a2a9b1;width:100%;clear:both;font-size:88%;text-align:center;padding:1px;margin:1em auto 0}.mw-parser-output .navbox .navbox{margin-top:0}.mw-parser-output .navbox+.navbox,.mw-parser-output .navbox+.navbox-styles+.navbox{margin-top:-1px}.mw-parser-output .navbox-inner,.mw-parser-output .navbox-subgroup{width:100%}.mw-parser-output .navbox-group,.mw-parser-output .navbox-title,.mw-parser-output .navbox-abovebelow{padding:0.25em 1em;line-height:1.5em;text-align:center}.mw-parser-output .navbox-group{white-space:nowrap;text-align:right}.mw-parser-output .navbox,.mw-parser-output .navbox-subgroup{background-color:#fdfdfd}.mw-parser-output .navbox-list{line-height:1.5em;border-color:#fdfdfd}.mw-parser-output .navbox-list-with-group{text-align:left;border-left-width:2px;border-left-style:solid}.mw-parser-output tr+tr>.navbox-abovebelow,.mw-parser-output tr+tr>.navbox-group,.mw-parser-output tr+tr>.navbox-image,.mw-parser-output tr+tr>.navbox-list{border-top:2px solid #fdfdfd}.mw-parser-output .navbox-title{background-color:#ccf}.mw-parser-output .navbox-abovebelow,.mw-parser-output .navbox-group,.mw-parser-output .navbox-subgroup .navbox-title{background-color:#ddf}.mw-parser-output .navbox-subgroup .navbox-group,.mw-parser-output .navbox-subgroup .navbox-abovebelow{background-color:#e6e6ff}.mw-parser-output .navbox-even{background-color:#f7f7f7}.mw-parser-output .navbox-odd{background-color:transparent}.mw-parser-output .navbox .hlist td dl,.mw-parser-output .navbox .hlist td ol,.mw-parser-output .navbox .hlist td ul,.mw-parser-output .navbox td.hlist dl,.mw-parser-output .navbox td.hlist ol,.mw-parser-output .navbox td.hlist ul{padding:0.125em 0}.mw-parser-output .navbox .navbar{display:block;font-size:100%}.mw-parser-output .navbox-title .navbar{float:left;text-align:left;margin-right:0.5em}body.skin--responsive .mw-parser-output .navbox-image img{max-width:none!important}@media print{body.ns-0 .mw-parser-output .navbox{display:none!important}}

/* end https://en.wikipedia.org/ */

</style></div><div role="navigation" class="navbox" aria-labelledby="Routing_software207" style="padding:3px"><table class="nowraplinks mw-collapsible autocollapse navbox-inner" style="border-spacing:0;background:transparent;color:inherit"><tbody><tr><th scope="col" class="navbox-title" colspan="2"><style data-mw-deduplicate="TemplateStyles:r1239400231">

/* start https://en.wikipedia.org/ */

.mw-parser-output .navbar{display:inline;font-size:88%;font-weight:normal}.mw-parser-output .navbar-collapse{float:left;text-align:left}.mw-parser-output .navbar-boxtext{word-spacing:0}.mw-parser-output .navbar ul{display:inline-block;white-space:nowrap;line-height:inherit}.mw-parser-output .navbar-brackets::before{margin-right:-0.125em;content:"[ "}.mw-parser-output .navbar-brackets::after{margin-left:-0.125em;content:" ]"}.mw-parser-output .navbar li{word-spacing:-0.125em}.mw-parser-output .navbar a>span,.mw-parser-output .navbar a>abbr{text-decoration:inherit}.mw-parser-output .navbar-mini abbr{font-variant:small-caps;border-bottom:none;text-decoration:none;cursor:inherit}.mw-parser-output .navbar-ct-full{font-size:114%;margin:0 7em}.mw-parser-output .navbar-ct-mini{font-size:114%;margin:0 4em}html.skin-theme-clientpref-night .mw-parser-output .navbar li a abbr{color:var(--color-base)!important}@media(prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .navbar li a abbr{color:var(--color-base)!important}}@media print{.mw-parser-output .navbar{display:none!important}}

/* end https://en.wikipedia.org/ */

</style><div id="Routing_software207" style="font-size:114%;margin:0 4em"><a href="List_of_router_firmware_projects" title="List of router firmware projects">Routing software</a></div></th></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="Operating_system" title="Operating system">Operating systems</a> and <a href="Network_operating_system" title="Network operating system">network operating systems</a></th><td class="navbox-list-with-group navbox-list navbox-odd hlist" style="width:100%;padding:0"><div style="padding:0 0.25em"></div><table class="nowraplinks navbox-subgroup" style="border-spacing:0"><tbody><tr><th scope="row" class="navbox-group" style="width:1%"><a href="Linux_kernel" title="Linux kernel">Linux</a>- based</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"></div><table class="nowraplinks navbox-subgroup" style="border-spacing:0"><tbody><tr><th scope="row" class="navbox-group" style="width:1%"><a href="Free_and_open-source_software" title="Free and open-source software">Entirely free</a></th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Endian_Firewall" title="Endian Firewall">Endian</a></li>

<li><a href="Floppyfw" title="Floppyfw">Floppyfw</a></li>

<li><a href="IPFire" title="IPFire">IPFire</a></li>

<li><a href="LibreCMC" title="LibreCMC">libreCMC</a></li>

<li><a href="OpenWrt" title="OpenWrt">OpenWrt</a></li>

<li><a href="Zeroshell" title="Zeroshell">Zeroshell</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="Proprietary_software" title="Proprietary software">Partly proprietary</a></th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Ubiquiti" title="Ubiquiti">AirOS and EdgeOS</a></li>

<li><a href="AlliedWare_Plus" title="AlliedWare Plus">Alliedware Plus</a></li>

<li><a href="ExtremeXOS" title="ExtremeXOS">ExtremeXOS</a></li>

<li><a href="Fritz!Box" title="Fritz!Box">FRITZ!Box</a></li>

<li><a href="MikroTik#RouterOS" title="MikroTik">RouterOS</a></li>

<li><a href="Smoothwall" title="Smoothwall">Smoothwall</a></li>

<li><a href="Tomato_(firmware)" title="Tomato (firmware)">Tomato</a></li>

<li><a href="Vyatta" title="Vyatta">Vyatta</a></li></ul>

</div></td></tr></tbody></table><div></div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="FreeBSD" title="FreeBSD">FreeBSD</a>- based</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"></div><table class="nowraplinks navbox-subgroup" style="border-spacing:0"><tbody><tr><th scope="row" class="navbox-group" style="width:1%"><a href="Free_and_open-source_software" title="Free and open-source software">Entirely free</a></th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<li><a href="OPNsense" title="OPNsense">OPNsense</a></li>

<li><a href="PfSense" title="PfSense">pfSense</a></li></ul>

<ul><li><a href="Junos_OS" title="Junos OS">Junos OS</a></li></ul>

</div></td></tr></tbody></table><div></div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="Proprietary_software" title="Proprietary software">Proprietary</a></th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Cisco_IOS" title="Cisco IOS">Cisco IOS</a></li>

<li><a href="Extreme_Networks" title="Extreme Networks">ExtremeWare</a></li>

<li><a href="Alcatel-Lucent" title="Alcatel-Lucent">TiMOS</a></li>

</div></td></tr></tbody></table><div></div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Routing daemons</th><td class="navbox-list-with-group navbox-list navbox-even hlist" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Babel_(protocol)" title="Babel (protocol)">Babel</a></li>

<li><a href="FRRouting" title="FRRouting">FRRouting</a></li>

<li><a href="GNU_Zebra" title="GNU Zebra">GNU Zebra</a></li>

<li><a href="OpenBGPD" title="OpenBGPD">OpenBGPD</a></li>

<li><a href="OpenOSPFD" title="OpenOSPFD">OpenOSPFD</a></li>

<li><a href="Quagga_(software)" title="Quagga (software)">Quagga</a></li>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Other software</th><td class="navbox-list-with-group navbox-list navbox-odd hlist" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Captive_portal" title="Captive portal">Captive portal</a></li>

<li><a href="Neighbornode" title="Neighbornode">Neighbornode</a></li>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Related articles</th><td class="navbox-list-with-group navbox-list navbox-even hlist" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="List_of_router_and_firewall_distributions" title="List of router and firewall distributions">List of router and firewall distributions</a></li>

<li><a href="List_of_router_firmware_projects" title="List of router firmware projects">List of router firmware projects</a></li>

<li><a href="National_Security_Agency#Software_backdoors" title="National Security Agency">National Security Agency#Software backdoors</a></li></ul>

</div></td></tr></tbody></table></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .tooltip-dotted{border-bottom:1px dotted;cursor:help}

/* end https://en.wikipedia.org/ */

</style></div><div role="navigation" class="navbox authority-control" aria-labelledby="Authority_control_databases_frameless&#124;text-top&#124;10px&#124;alt=Edit_this_at_Wikidata&#124;link=https&#58;//www.wikidata.org/wiki/Q5318#identifiers&#124;class=noprint&#124;Edit_this_at_Wikidata1476" style="padding:3px"><table class="nowraplinks hlist mw-collapsible autocollapse navbox-inner" style="border-spacing:0;background:transparent;color:inherit"><tbody><tr><th scope="col" class="navbox-title" colspan="2"><div id="Authority_control_databases_frameless&#124;text-top&#124;10px&#124;alt=Edit_this_at_Wikidata&#124;link=https&#58;//www.wikidata.org/wiki/Q5318#identifiers&#124;class=noprint&#124;Edit_this_at_Wikidata1476" style="font-size:114%;margin:0 4em">Authority control databases </div></th></tr><tr><th scope="row" class="navbox-group" style="width:1%">National</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"><ul><li><a rel="nofollow" class="external text" href="https://d-nb.info/gnd/4298524-9">Germany</a></li><li><a rel="nofollow" class="external text" href="https://id.loc.gov/authorities/sh99004539">United States</a></li><li><a rel="nofollow" class="external text" href="https://catalogue.bnf.fr/ark:/12148/cb135602665">France</a></li><li><a rel="nofollow" class="external text" href="https://data.bnf.fr/ark:/12148/cb135602665">BnF data</a></li><li><a rel="nofollow" class="external text" href="https://aleph.nkp.cz/F/?func=find-c&local_base=aut&ccl_term=ica=ph229475&CON_LNG=ENG">Czech Republic</a></li><li><a rel="nofollow" class="external text" href="https://www.nli.org.il/en/authorities/987007537205405171">Israel</a></li></ul></div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Other</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em"><ul><li><a rel="nofollow" class="external text" href="https://lux.collections.yale.edu/view/concept/8311cc50-9a9e-4601-8d01-6289e8a3bbad">Yale LUX</a></li></ul></div></td></tr></tbody></table></div></div><div><div class="zim-footer">

This article is issued from <a class="external text" title="Last edited on 2025-07-06" href="https://en.wikipedia.org/wiki/?title=Router_(computing)&oldid=1299178247">Wikipedia</a>. The text is available under <a class="external text" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Creative Commons Attribution-Share Alike 4.0</a> unless otherwise noted. Additional terms may apply for the media files.

</div>

</div></div>

</div>

</main>

</div>

</body></html>